chore(maintainer): declare scout.survey broken_only in policy - #37

Declare the survey/scout mode in the maintainer policy

• Picked up
• Surveying the repo — 2026-11-09 13:23 UTC
• Working — 2026-11-09 13:23 UTC
• Pull request opened — chore(maintainer): declare scout.survey broken_only in policy #37 — 2026-11-09 13:23 UTC
• Done

Work landed on #37 — watching it toward merge.

58s · 10 tool calls

Sessions: coding run

🤖 developerz.ai, an automated agent, not a human — hv-dedicated-ci-1 (developerz-ai[bot]) · model claude-sonnet-5-5 on router.ai.developerz.ai

✅ Reviewed — nothing blocking

0 actionable comment(s) · grounded on your code

_{⚠️ 1 config note(s): test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against}

_{⏱ 29s wall clock · deepseek-v4.1-flash via router · 1 model call(s) · 806 output token(s)}

_{🤖 developerz.ai — automated review, running on your model and your box.}

Waiting on the repository owner: this pull request changes a gate file, which the platform does not merge by itself.

It changes .dz/maintainer/maintainer.yml.

The merge check refused the edit: .dz/maintainer/maintainer.yml: a modified policy has no declared transform — only a new one on a repo with none for #37 — proof path: git checkout ef9f7cec1c89410e5f3538e561d3970f36ba32b6 -- .dz/maintainer/maintainer.yml and push — a head that leaves every gate path as the base has it needs no proof, and the rest of the PR merges; or keep only an edit that is exactly a declared transform below. When the gate edit IS the goal, no head of ours proves it: the owner applies it. the PR is re-proved when its head changes, when the platform changes its gate-path transforms or templates, and on the hourly re-check; no .maintainer.yml key and no approval releases it — a workflow edit proves only as a tag pin, a permissions narrowing or a platform template, an added .mcp.json or reviewer prompt only as the platform template, a modified .mcp.json only as the platform adding its managed servers to the base file and touching nothing of the maintainer's, and a policy file only as a NEW .dz/maintainer/maintainer.yml on a repo with none that grants no more than the account's posture default

Every file it changes is one of those files, so there is nothing to re-file without them.

To take it, merge it on GitHub. To have the platform merge it, push a narrower edit: a new head is checked again and merged when the check passes. Nothing here is re-tried or closed automatically, and no email is sent; the pull request is listed with the stuck pull requests.

🤖 Posted by developerz.ai — an automated agent, not a human.